-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NMS-16486: Extracted caches from DocumentEnricherImpl #7397
Conversation
christianpape
commented
Aug 28, 2024
- JIRA: https://opennms.atlassian.net/browse/NMS-16486
dfa7fb5
to
1799458
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beside the comment, nothing I can complain about :)
http://aries.apache.org/schemas/blueprint-ext/blueprint-ext-1.1.xsd | ||
"> | ||
<!-- Configuration properties --> | ||
<cm:property-placeholder id="cacheConfigProperties" persistent-id="org.opennms.features.telemetry.protocols.common" update-strategy="reload"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to create a documentation enhancement to add all these new configuration properties to the docs and make it a requirement when we decide to merge this into an official release. It's not a blocker for the merge into NMS-16375.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Yes, we have to add these to the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main itch is the naming. The NodeMetadataCache
gives out NodeInfo
. Also the package naming does not reflect the maven project structure. NodeInfo
is located in .../protocols/common/cache
where as protocols/common
and protocols/cache
both exist.
Yes, you are totally right. The common.cache is a leftover of changes I reverted. I'll fix that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
a6e7326
to
16a33b7
Compare
16a33b7
to
15df160
Compare
15df160
to
1d723d7
Compare